At the moment, the batching means that when an image is created, the main thread interprets that as separate images and creates a bunch of invalid files with the same name. To stop this happening, we probably need to modify the response on the frontend to ensure that the batched writes all hit the same file and append to rather than overwrite the existing content. The question we will have is when do we want existing files to be overwritten and when do we want them to be appended to and how can we tell? For example, if it's another batch of binary from the same request then we might want it to append, whereas if it's another request from the user, we might want it to overwrite. Maybe we need some metadata to give a unique ID to the request?

Question: How do we want to deal with image files created by a user who is not logged in? Do we want to let them save the image to the bucket anyway? Or should it be saved in localStorage somehow? An MVP option could be to tell them they have to log in to add images to the project, although not ideal.

Also, we may need some changes on the API side to stop writing to a filename that already exists creating multiple files with the same name in the same project. Can we have an update image endpoint as well as a create image endpoint? And if so, would we overwrite the original image in the bucket? In other words, how would this work in practice?

Work out why updating an image only works after the page has been reloaded, otherwise it creates a second image with the same name.